AWS requirements

Amazon Web Services

The page lists the requirements for deploying to Amazon's cloud solution Amazon Web Services (AWS).

Suggested requirements for AWS.

If deploying to AWS, ensure that you have the following:

• AWS Virtual Private Networking (VPC)
  • Subnets, routing tables, internet access, etc.
  • Load balancing, WAF, etc. for ingress into Kubernetes
• AWS Elastic Kubernetes Service (EKS)
  • EKS Cluster v1.29
  • Pod Identity Agent
  • Network Policy Implementation (e.g. Calico or VPC CNI)
  • Custom Metrics Collection Implementation, e.g. Prometheus as kube-prometheus-stack and Prometheus Adapter as prometheus-adapter
  • Block storage CSI Provider
  • Shared file system CSI Provider
• AWS Relational Database System (RDS)
  • PostgreSQL v14
  • RDS Proxy
• AWS ElastiCache
  • Redis OSS v7
• AWS Managed Service for Kafka (MSK)
  • Kafka v3.7
• AWS MQ (AMQ)
  • ActiveMQ v5.18
• MongoDB Atlas
  • MongoDB v6
  • VPC Peering to AWS application/Kubernetes VPC
• Neo4j Standalone Helm Chart
  • Neo4J v4.4 - Needs two standalone clusters (neo4j1 and neo4j2)
• AWS CloudFront
  • Refer to the AWS CloudFront Requirements page for details.
• AWS S3
  • Refer to the AWS S3 Requirements page for details.
• SMTP (no dedicated cluster needed; simply an SMTP endpoint for delivering emails). While AWS has the Simple Email Service (SES), most customers will have an existing SMTP server for this use.